Add generic device support to dft domain through portFFT #570
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
s-Nick
force-pushed
the
generic_device_dft
branch
from
3a9ffbd
to
907dc5e
Compare
s-Nick
changed the title
Rbiessy
approved these changes
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is the continuation of PR #566 and it is based on it.
It adds generic devices support by enabling portFFT and generic device the same way it is done for portBLAS.
Checklist
All Submissions
Following logs show that all domains still work properly:
portfft_log.txt
arc_blas_log.txt
cufft_log.txt
arc_lapack_log.txt
arc_rng_log.txt
New features
Have you provided motivation for adding a new feature?
Same reason added to Add generic device and initial support in portBLAS #566
Have you added relevant tests?
Generic device doesn't require new tests